All messages (administrative or application) are preceded by a Standard Header. In addition to providing the identification of FIX Session participants, the Standard Header identifies the Message Type (Tag 35), Message Length (Tag 9), Origination times (Tag 52 and Tag 122) and Message Sequence order (Tag 34). The Standard Header also offers additional information on FIX Session authentication, resent messages, duplicated message and message routing and delivery.
| ag | Field Name | Req'd | Comments | | BeginString | Y | FIX.4.4 (Always unencrypted, must be first field in message) |
|---|
| BodyLength | Y | (Always unencrypted, must be second field in message) |
| 5 | MsgType | Y | (Always unencrypted, must be third field in message) |
| 9 | SenderCompID | Y | (Always unencrypted) |
| 6 | TargetCompID | Y | (Always unencrypted) |
| 15 | OnBehalfOfCompID | N | Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.) |
| 28 | DeliverToCompID | N | Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.) |
| 0 | SecureDataLen | N | Required to identify length of encrypted section of message. (Always unencrypted) |
| 1 | SecureData | N | Required when message body is encrypted. Always immediately follows SecureDataLen field. |
| 4 | MsgSeqNum | Y | (Can be embedded within encrypted data section.) |
| 0 | SenderSubID | N | (Can be embedded within encrypted data section.) |
| 42 | SenderLocationID | N | Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.) |
| 7 | TargetSubID | N | “ADMIN” reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.) |
| 43 | TargetLocationID | N | Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.) |
| 16 | OnBehalfOfSubID | N | Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.) |
| 44 | OnBehalfOfLocationID | N | Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.) |
| 29 | DeliverToSubID | N | Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.) |
| 45 | DeliverToLocationID | N | Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.) |
| 3 | PossDupFlag | N | Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)| |
| 7 | PossResend N | Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.) |
| 2 | SendingTime | Y | (Can be embedded within encrypted data section.) |
| 22 | OrigSendingTime | N | Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.) |
| 12 | XmlDataLen | N | Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.) |
| 13 | XmlData | N | Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) |
| 47 | MessageEncoding | N | Type of message encoding (non-ASCII characters) used in a message’s “Encoded” fields. Required if any “Encoding” fields are used. |
| 69 | LastMsgSeqNumProcessed | N | The last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty. |
| 27 | NoHops | N | Number of repeating groups of historical “hop” information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops. |
| 28 | HopCompID Group | N | Third party firm which delivered a specific message either from the firm which originated the message or from another third party (if multiple “hops” are performed). It is recommended that this value be the SenderCompID (49) of the third party. |
| 29 | HopSendingTime | N | Time that HopCompID (628) sent the message. It is recommended that this value be the SendingTime (52) of the message sent by the third party. |
| 30 | HopRefID | N | Reference identifier assigned by HopCompID (628) associated with the message sent. It is recommended that this value be the MsgSeqNum (34) of the message sent by the third party. |